triPOS®

triPOS Logs

Logging with tp-request-id

The logs provided by triPOS now track requests by tp-request-id as they process through the system.

Log Example Before:
2017-05-09 11:31:41,377 [STP SmartThreadPool Thread #2168] triPOS INFO - Express state changing from SettingUpRequest to WaitingResponse in MoveNext
2017-05-09 11:31:41,649 [32] triPOS INFO - Express state changing from WaitingResponse to ParsingResponse in HandleResponse

Log Example After: <

2017-05-09 11:31:41,377 [STP SmartThreadPool Thread #2168] triPOS INFO - 61105169-2723-451b-bcc5-26eec21e11d3 Express.cs.SendState: Express state changing from SettingUpRequest to WaitingResponse in MoveNext
2017-05-09 11:31:41,649 [32] triPOS INFO - 61105169-2723-451b-bcc5-26eec21e11d3 Express.cs.SendState: Express state changing from WaitingResponse to ParsingResponse in HandleResponse

Rolling Logs Behavior

triPOS provides the following list of logs: trace, debug, info, warn, error, fatal, and verbose. When a log reaches the maximun default file size of 5MB, it will generate a backup, and the rolled files will be named as X.log.1, X.log.2, up to 5; with the exception of the Verbose.log which will retain up to 20 files. Files older than the maximun of 5 or 20 (verbose.log) will automatically be deleted.

The default number of files retained and the file size can be customized via the log4net.config. To change the number of retained files and/or the file size:

  1. Open the log4net.config file.
  2. Locate the log you'd like to change.
  3. Update the following values to fit your business needs:
    4. maxSizeRollBackups value="5"
    maximumFileSize value="5MB"
  4. Save the changes.
  5. Restart triPOS.